Skip to content

feat: MaveMD score set landing table redesign - #719

Open
bencap wants to merge 2 commits into
release-2026.3.0from
feature/bencap/694/mavemd-landing-scoreset-table
Open

feat: MaveMD score set landing table redesign#719
bencap wants to merge 2 commits into
release-2026.3.0from
feature/bencap/694/mavemd-landing-scoreset-table

Conversation

@bencap

@bencap bencap commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

Summary

Redesigns the MaveMD landing-page score set table (SearchVariantsScreen.vue). Implements the four improvements in #694, plus a density/readability pass. No backend changes — all data is already on the ScoreSet objects.

What changed

  • Gene filter. A typeahead inlined with the section heading filters the table by gene, case-insensitive substring. It searches the whole collection rather than the 8-gene preview; clearing it restores the preview.
  • Merged Score set + Publication column. One column now shows the title (links to the score set) above the citation (links out to the publication). This fixes the old Publication column, which linked back to the score set page instead of the article.
  • Calibration status. The opaque X / Y badge is replaced with a labeled status — None, Uncalibrated, Research use only, or Calibrated — linking to the calibrations page, with a bulleted tooltip on the column header explaining each state.
  • Variants column. Shows numVariants with a thousands separator.
  • Density pass. Larger text, more row padding, and each score set's short description, so rows read as cards rather than sparse lines.

Calibration status semantics

A score set is Calibrated as soon as one non-RUO calibration assigns ACMG/AMP evidence strengths — it does not require every calibration to carry evidence. The one caveat is research-use-only: when the only evidence-bearing calibrations are RUO, the badge reads Research use only rather than Calibrated.

Condition Label
No calibrations None
Calibrations exist, none assign ACMG evidence Uncalibrated
Has evidence, but every evidence-bearing calibration is RUO Research use only
≥1 non-RUO calibration assigns ACMG evidence Calibrated

Refactor (first commit)

Publication-URL resolution is extracted into src/lib/publication (getPublicationUrl: url → DOI → PubMed) and adopted in MvPublicationsSection and PublicationIdentifierView, which previously linked out only when the identifier carried a resolved url. Both now get the DOI / PubMed fallback.

Screenshots

Before:
Screenshot 2026-08-26 at 2 46 04 PM

After:
Screenshot 2026-08-26 at 2 46 44 PM

bencap added 2 commits August 26, 2026 14:38
Add getPublicationUrl to src/lib/publication (url -> DOI -> PubMed
fallback) and use it in MvPublicationsSection and
PublicationIdentifierView, which previously linked out only when the
identifier carried a resolved url. Both now fall back to a doi.org or
pubmed.ncbi.nlm.nih.gov link. Add unit tests for the helper.
Rework the MaveMD score set table for a collection that has grown past
80 datasets, per #694.

- Add a gene typeahead filter, inlined with the section heading, that
  searches the whole collection rather than just the 8-gene preview.
- Merge the Score set and Publication columns into one: the title links
  to the score set and the citation links out to the publication. This
  fixes the old Publication link, which pointed back at the score set
  page instead of the article.
- Replace the opaque "X / Y" calibration badge with a labeled status:
  None, Uncalibrated, Research use only, or Calibrated. A score set
  counts as Calibrated once one non-RUO calibration assigns ACMG
  evidence; RUO-only evidence is flagged rather than shown as clinical.
- Add a Variants column showing the variant count.
- Enlarge and pad the rows and add each score set's short description.
- Explain the calibration states in a bulleted header tooltip.

Score-set publication links resolve through the shared getPublicationUrl
helper. Add unit tests for the score-set helper.
@bencap
bencap requested a review from jstone-dev August 26, 2026 21:50
@bencap bencap linked an issue Aug 26, 2026 that may be closed by this pull request
10 tasks
@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 10.822% (+0.5%) from 10.274% — feature/bencap/694/mavemd-landing-scoreset-table into release-2026.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UX: Redesign MaveMD landing page scoreset table

2 participants